<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Sprint Planning Meeting</title>
<script type="text/javascript" language="javascript" src="func.js"></script>
</head>

<body>
<p>The work to be performed in the Sprint is planned at the Sprint Planning Meeting. This plan is created by the collaborative work of the entire Scrum Team.</p>
<a href="#" id="a" onclick="show('content', 'block');">Read more...</a>
<div id="content" style="display: none;">
<img src="../drawable/planning_meeting.jpg" width="100%" title="planning meeting"/>
    <p>The Sprint Planning Meeting is time-boxed to eight hours for a one-month Sprint. For shorter Sprints, the event is proportionately shorter. For example, two-week Sprints have four-hour Sprint Planning Meetings.</p>
    <p>The Sprint Planning Meeting consists of two parts, each one being a time-box of one half of the Sprint Planning Meeting duration. The two parts of the Sprint Planning Meeting answer the following questions, respectively:
    <ul>
    <li>What will be delivered in the Increment resulting from the upcoming Sprint?</li>
    <li>How will the work needed to deliver the Increment be achieved?</li>
    </ul>
    </p>
    <b style="color: blue">Part One: What will be done this Sprint?</b>
    <img src="../drawable/planning_meeting_3.jpg" width="100%" title="planning meeting"/>
    <p>In this part, the Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner presents ordered Product Backlog items to the Development Team and the entire Scrum Team collaborates on understanding the work of the Sprint.</p>
    <p>The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team. The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.</p>
    <p>After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.</p>
    <b style="color: blue">Part Two: How will the chosen work get done?</b>
    <img src="../drawable/planning_meeting_2.jpg" width="100%" title="planning meeting"/>
    <p>Having selected the work of the Sprint, the Development Team decides how it will build this functionality into a "Done" product Increment during the Sprint. The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog,</p>
    <p>The Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product increment. Work may be of varying size, or estimated effort. However, enough work is planned during the Sprint Planning meeting for the Development Team to forecast what it believes it can do in the upcoming Sprint. Work planned for the first days of the Sprint by the Development Team is decomposed to units of one day or less by the end of this meeting. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during the Sprint Planning Meeting and as needed throughout the Sprint.</p>
    <p>The Product Owner may be present during the second part of the Sprint Planning Meeting to clarify the selected Product Backlog items and to help make trade-offs. If the Development Team determines it has too much or too little work, it may renegotiate the Sprint Backlog items with the Product Owner. The Development Team may also invite other people to attend in order to provide technical or domain advice.</p>
    <p>By the end of the Sprint Planning meeting, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.</p>
    <b style="color: blue">Sprint Goal</b>
    <p>The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint.</p>
    <p>As the Development Team works, it keeps this goal in mind. In order to satisfy the Sprint Goal, it implements the functionality and technology. If the work turns out to be different than the Development Team expected, then they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.</p>
    <p>The Sprint Goal may be a milestone in the larger purpose of the product roadmap.</p>
    <img src="../drawable/planning_meeting_4.jpg" width="100%" title="planning meeting"/>
</div>
</body>
</html>
